Re: retrieving varchar size - Mailing list pgsql-interfaces

From Michael Hirohama
Subject Re: retrieving varchar size
Date
Msg-id l03110705b1698217f47d@[204.179.136.2]
Whole thread Raw
In response to Re: [HACKERS] Re: [INTERFACES] retrieving varchar size  (Bruce Momjian <maillist@candle.pha.pa.us>)
Responses Re: [HACKERS] Re: retrieving varchar size  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: [HACKERS] Re: retrieving varchar size  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-interfaces
The historical reason why the POSTGRES backend is required to send multiple
result sets is to support cursors on queries involving type inheritance and
anonymous target lists.

    begin
    declare c cursor for
        select e.oid, e.* from EMP* e
    fetch 10 in c
    ...

To handle the command sequence above, frontend applications would need to
be provided with a new result descriptor when the "fetch 10 in c" crosses a
result set boundary.



pgsql-interfaces by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] Re: [INTERFACES] retrieving varchar size
Next
From: dg@illustra.com (David Gould)
Date:
Subject: Re: [HACKERS] Re: [INTERFACES] retrieving varchar size